PagerDuty

PagerDuty is a key monitoring and alerting component that we use org wide for Engineering Teams. The specific business problems that we address by using PagerDuty are
1. Org Wide alerting for critical components like error handling, out-of-memory detections etc
2. Infra based alerts to identify areas where load is a lot, for example if there are excessive arguments on an sidekiq queue
3. Low priority alerting of components as well

I use PagerDuty to monitor our product and alert us when a threshold exceeds. PagerDuty is highly helpful in alerting on time so that I can take action without any delay. Also, it helps in scheduling shifts for team members seamlessly. PagerDuty dashboards are useful to check various metrics.

We majorly use PD for incident management and bug resolutions. PD has great integration with Slack that is very helpful for quick updates on the tickets directly from Slack. The monitoring and consolidation of issues is very convenient and is able to provide us with good visibility into related issues as well.

I am part of the engineering team which owns the 24/7 on-call suport for all our services in the production and we use the pagerduty to effectively manage our on-call support and define the escalation policies.
Using pagerduty its easy to notify on-call person via message and call and we liked the feature where we can define after how much duration notification should be delivered to what medium and to whom. Also its easy to override the on-call schedule for a specified duration and manage the overall team on-call schedule.
Also pagerduty integrates very well with the other software we use like mail, Slack and their Android app works seamlessly for me.

We started looking for a monitoring / alerting tool as the tool we were using was getting too expensive and licenses agreement was expiring. PagerDuty was rolled out for some teams primarily to create and alert the operations teams for application and infrastructure related issues. Using PagerDuty not only did we implement the existing monitoring as is, but a lot of tasks were automated. PagerDuty also helped us removed the dependency of monitoring team as the monitoring and callback feature was available in PagerDuty as IVR. This decision not only saved us some money, but we also reduced the Incident response time by 50%. Soon we updated to the premium license which included additional AI features and now we are utilizing even more features and integrations supported by PagerDuty.

We use PagerDuty as the single source for alerting our support teams when production issues arise. We love the fact that we can be notified via text, in-app notifications, phone calls (or even all three if you like). It integrates seamlessly with our cloud-based monitoring vendors like pingdom, Cronitor, and AlertBot.

We use PagerDuty as an on call alerting tool to let us know when inbound sales leads or messages come to the company sales/info email. We are required to respond in a certain amonunt of time and PagerDuty helps us do that

I manage a team that supports critical applications for a university. Before implementing PagerDuty, we encountered issues overnight and were not aware that there was a service failure until the morning, and/or if students informed us. We paired New Relic with PagerDuty, so that when specific metrics exceed the set thresholds, integration notifies PagerDuty and sends an alert to the relevant on-call support member.

Since implementing, PagerDuty has provided immediate alerting when a problem exists, and has allowed us to restore service (or prevent service loss in some cases) to minimise disruption.

The PagerDuty platform is used across the organization for on-call management, event/alert management and automated escalations. The platform solved a significant inefficiency within the business related to on-call and escalations. Prior to PagerDuty, escalations were manual and not well documented. This made it difficult to hold people accountable and properly document problems. Through PagerDuty's escalation policies, on-call schedules and general workflow automation capabilities, the problem was solved fairly quick. Because our on-call team members are paid each time they answer an on-call request, this made tracking the notifications much easier.

I'm using PagerDuty as administrator and Manager. Followings are the operations I'm doing.

• Create/update/delete the teams.
• Create escalations policies.
• Create schedule for teams

Business cases:

• Incident Management
• Alerting management
• Page on-call users.
• Integrations with 3rd party applications like Slack, AWS, Emails, and Jira.
• Configure workflows in 3rd parties for e.g. on-call person schedule for a team in Slack.

We primarily use PagerDuty for on-call alerting. We have a number of monitoring platforms that are integrated with PagerDuty or send emails to escalation policies for various teams across the org. We are able to maintain a schedule of individuals in each team and we are able to escalate alerting should current on-call fail to pick up the page.

PagerDuty for us is a critical tool, rather it's for after-hours paging or raising awareness of a critical issue during the day. Part of being an IT is managing multiple systems, which can be on-prem or in the cloud, and when these systems have issues or are down, we need to get timely alerts from our RMM tools. PagerDuty makes this possible; using their application, we can set on-call rotations, backups, holidays, and substitutes and make sure that we have a hand on the wheel when things get bumpy. PD can tie directly into applications as a 3rd party plugin, which as the #1 solution, is widely supported, or there is the option for SMTP triggers. Businesses need PD, so IT can get those critical alerts to keep the business on track. I have tried comparable solutions and always find myself coming back to PD.

PagerDuty handles our on-call alerting. This means when we have production level outages or issues, they get sent to PagerDuty and PagerDuty has a schedule for our on-call engineers and can send texts, emails, Slack notifications, and phone calls to the correct person to handle. Within PagerDuty we setup schedules so we know who is primary and who is secondary on-call so that way we always have coverage.

We utilize PagerDuty for incident response -- so if something critical happens where we literally need to wake people up, this is how we do it. We have it integrated with our other systems so that there is a clear workflow and notification associated with any triggering event. Specifically, if an incident of a certain severity occurs, PagerDuty sets off an alert across multiple systems in support and engineering, pinging them on their phones, and mobilizing a response team

We use pagerduty in our clients information system to recover, analyse and create alerts based on the cloud provider logging service.
PagerDuty is then configured to send alerts to specific users

We used PagerDuty primarily to manage on-call rotations across multiple engineering and support teams and to route automated alerts to the correct people in correct engineering teams. We also used it occasionally to route urgent (24/7) customer support requests to the correct people in product support departments. Additionally PagerDuty escalated incidents when they were not acknowledged or resolved promptly, and we used it as a tool to analyze data about the causes of frequent issues.

Pagerduty is used both for alerting teams to application problems that are identified by our monitoring and observability platforms as well as engaging on-call resources into an active incident bridge for real-time troubleshooting and remediation.

We use PagerDuty for engineering incident management. It alerts us about issues in our production pipeline, and offers escalation policies and alerts so we can address the SEVs in time. By paging the on-call engineer to look into blockers in a timely manner, it allows us to improve our service metrics.

We use it for off-hours support and managing notification schedules of off-hours support staff. It simplifies management with notification of schedule hand-off and backup coverage.

PagerDuty is used as an event management platform. All monitoring tools used are supposed to feed into PD and the logic of whether the alerts are high / low etc are performed in PagerDuty . This makes it easier to manage and each team works in a similar way.

PagerDuty is an incredibly tool for managing response and incidents and I find it very effective and efficient. To people who are non technical skilled it is very friendly and easy to use since it has dashboard that is easy to understand and straightforward. When it comes to observation the app top notch like one can set alerts with notifications in way that when something goes wrong there is a fast action. It is crucial to have product that will aid in monitoring your program development architecture so as to detect, diagnose and resolve any incidents which may have adverse effects on your final products.

We use PaperDuty to manage our production support on-demand schedule. With the tool, we plan the team availability for each group of services. When we're on call PagerDuty notifies us (via slack, mobile app, and email) about the issues so we don't lose any alerts, and also it handles the escalation policy as needed automatically

We're using PagerDuty for reliability services such as service monitoring, on-call handling, on-call alerting and helps in managing infrastructure based alerts and outages in our systems automatically.

In my current and previous production system Datadog and Sumologic are tools used for observability and they are configured to send alerts to PagerDuty for errors or warning as per user/customer specific thresholds. We are using webhooks to implement this integration. We have customer specific rule sets and thresholds.

PagerDuty is the leading digital operations management platform for businesses, PagerDuty is an end-to-end incident management and response platform that provides developers, IT operations, and business stakeholders the insights they need to resolve and prevent business-impacting incidents quickly . We use Pager Duty as ticketing tool for my company , we have other products in the infrastructure and any alerts will go to Pager Duty creating tickets which then can be looked upon for resolution.